Three issues surfaced while building the working examples (wasmCloud
#5276 and typescript wasmCloud#678) that the quickstart prose walks users
through; this catches the docs up to what actually compiles.

- Rust world.wit: drop `export wasi:http/incoming-handler@0.2.9;`
  with a [!code --] strikethrough marker. wstd's #[http_server] macro
  generates the http export internally; leaving it in world.wit while
  also calling wit_bindgen::generate! makes the component encoder
  fail (the macro and the manual binding generation race over the
  same export symbol). Add a :::note explaining why, since this is
  the kind of detail a first-time user wouldn't infer from the error.

- TS world.wit: revert lingering 0.2.9 → 0.2.6 in the persistent-
  storage section. PR wasmCloud#1204 fixed the earlier code block but missed
  this one; jco-std 0.1.x ships only the 0.2.6 adapter, so anything
  else trips the same ReferenceError already documented in
  bytecodealliance/jco#1245.

- Rust src/lib.rs: `atomics::increment(&bucket, &name, 1)` →
  `atomics::increment(&bucket, name, 1)`. `name` is already `&str`
  from the query parsing; passing `&name` makes it `&&str` and
  clippy's needless_borrow lint (which the wasmCloud workspace
  denies) rejects the build.

Plus, link each language's section to its CI-tested example:

- Rust → wasmCloud/wasmCloud/examples/http-hello-world-persistent-storage
- TS  → wasmCloud/typescript/examples/components/http-hello-world-hono-persistent-storage

The companion examples were added in wasmCloud/wasmCloud#5272 and
wasmCloud/typescript#668 (both merged); the standard `examples`
workflows on those repos rebuild them on every PR, so future drift
between this walkthrough and what actually compiles surfaces in CI.

Signed-off-by: Eric Gregory <eric@cosmonic.com>

Surfaced while validating the persistent-storage walkthrough end to
end: the not_found function shown in the Rust code block uses
`.unwrap()` (no [!code] markers, so it's meant to be unchanged
context), but the template scaffolds with `.map_err(Into::into)`
and the workspace lints set `unwrap_used = 'deny'`. `wash build`
(cargo build) passes the docs version, but `cargo clippy` rejects
it — and the docs-linked example also uses the .map_err form.

Restoring the .map_err(Into::into) shape so the docs reproduce the
template verbatim. Fixed in both occurrences (lines 74 and 303,
the level-1 and level-2 lib.rs blocks).

Signed-off-by: Eric Gregory <eric@cosmonic.com>